Repository navigation
Lesson: ApolloExplorer; pitfall: v4net.device full-size frames; V4 boot time - #55
Merged
Merged
Conversation
lessons/2026-11-apolloexplorer.md: what the ApolloExplorer 1.4.4 work learned. An "unstable network" was the V4 Ethernet driver; the AROSTCP and DOS sources answered how TCP_MAXSEG, socket timeouts and SystemTagList() priority behave; and what the AI got wrong on the way. os/pitfalls/v4net-full-size-frames-lost.md: v4net.device 3.0-beta never transmits a 1514-byte frame (1500-byte IP packet), which stalls any TCP connection that sends more than ~1.4 KB. Measured on a V4 UniCorn, Core 12856, ApolloOS R9.6; workaround with TCP_MAXSEG on the connected socket until the driver is fixed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The same v4net.device 3.0 bug shows under AmigaOS 3.9 with AmiTCP_NG 4.1.8, so it is the driver, not ApolloOS. AmiTCP_NG does not implement TCP_MAXSEG (EINVAL, "not yet"), so the per-socket workaround fails silently there; mtu=1492 in DEVS:NetInterfaces/V4net fixes it for every program (measured: all ApolloExplorer tests pass, 4.2 MB/s). The occasional packet loss seen under ApolloOS is removed from the pitfall: under AmigaOS 3.9 with the same driver and core there was none, so it is not the driver alone. The lesson keeps it as an open point and adds what the AI got wrong about it and about TCP_MAXSEG. guides/testing-on-v4-hardware.md: the V4 answered ping 34.4 s after power-on under AmigaOS 3.9 (15 s to ash under ApolloOS R9.5): poll every second and give up after 60 s, and note that nothing answers remotely unless ApolloExplorerSrv starts at boot. v4test.py power-cycle now polls every second for at most 60 s (was 5 s / 120 s). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
From the ApolloExplorer 1.4.4 work (WDrijver/ApolloExplorer#9), tested under ApolloOS and AmigaOS on the same V4:
os/pitfalls/v4net-full-size-frames-lost.md.v4net.device3.0-beta never transmits a 1514-byte Ethernet frame (a 1500-byte IP packet); 1512 bytes and smaller work.mtu=1492inDEVS:NetInterfaces/V4net, which covers every program. AmiTCP_NG does not implementTCP_MAXSEG.TCP_MAXSEGon the connected socket. It can only lower the negotiated MSS.lessons/2026-11-apolloexplorer.md. What the project learned:TCP_MAXSEG, socket timeouts andSystemTagList()priority behave in AROSTCP, AmiTCP_NG and ApolloOS DOS.SystemTagList()ignores anNP_Prioritytag.guides/testing-on-v4-hardware.md.ashunder ApolloOS R9.5).tools/v4/v4test.pypower-cycle. It now polls every second for at most 60 s (was every 5 s for 120 s).Evidence
v4net.device3.0, 2026-11-16:tests/aetest.pyin WDrijver/ApolloExplorertcp_usrreq.c,tcp_output.c,kern/uipc_socket.csrc/netinet/tcp_usrreq.c,src/net/ng_ifconfig.crom/dos/systemtaglist.c,createnewproc.cNotes for review
applies_to.os:[apolloos-r10, amigaos-3.9], but the ApolloOS measurements were on R9.6. The body and sources say so. AmigaOS 3.2 is untested.v4net.deviceis from the apollo-core SVN, not ApolloOS, and the bug is the same under AmigaOS, so the rule against ApolloOS-bug workarounds does not apply.SystemTagList()/NP_Prioritystays a lesson candidate until it is checked on AmigaOS 3.x.Checks
check_frontmatter.py,check_links.py,check_owners.py,check_saga_addresses.pyand markdownlint all pass locally;v4test.pycompiles.🤖 Generated with Claude Code